Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
I often come across terms like COB Server or COB Database. Can anyone please explain what is COB environment and how is it different from production or UAT environment.
I've found this, I think is useful to have it in mind. Cheers!
Dev-> Development environment. Only used for coding and developers can access.
SIT-> Software Integration Test environment, Integration test group that verifies initial integration tests, (not functionality test) should be application managers or technology project testers. Also may be developers but not preferred.
UAT-> User Acceptance Test environment. Functionality test, is done by dedicated UAT groups or end users. Environment should be identical with production env. Developers or other technology staff should not access to UAT. Only functionality testers have access.
COB-> Continuity Of Business environment for disaster recovery. Highly advised to be identical with production environment. Also user rights/access should be identical with prod. Also first production release may be tested here before actual prod implementation with an appropriate change management process.
Prod-> Production environment. Final release, after UAT approvals received and an appropriate change management process, release can be implemented here by dedicated implementers.
COB environment is a production like environment and if production environment is down then it is pointed to this environment
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 12 months ago.
Improve this question
Using a DACPAC to upgrade a data-tier application database is an 'in-place process' as per the documentation.
My question is, how do you go about updating your production databases?
Do you just apply the DACPAC directly to the production database, and then roll back if anything goes wrong?
Obviously you would test this first in a dev, test or staging environment but I'm wondering if there are any other options?
We used dacpacs, but always tested the rollout against a nearly identical dev/test/uat system first. For really sensitive prod rollouts, sometimes I'd generate the change script/report first to make sure it was going to do what I expected. If that looked good, I'd let it run. (sometimes the process needed advanced permissions from the CICD engine that I didn't have with my account)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am new to google cloud and I am going to start a project on it based on cloud functions and bigQuery
I googled to find answer to my questions to be prepared for it, I couldn't find articles about it.
In classic way of software development usually we have different environment for Dev,QA,Staging,UAT and production and for databases such as SQL Server, we keep the scripts in source control and we have different copy of database for each environment, for example on dev environment v1.6 we add a field to a table, and on QA environment v1.5 table doesn't have the field yet until we promote v1.6, and so on
Now my question is, in google cloud environment how we should have different environment and versioning, should it be 5 different projects? What about google cloud functions, how should I manage different code for different branches for same function (for example fixing a bug in a cloud function) ?
The environment strategy depends on the particular GCP product being used.
With Google App Engine apps, as you observed, multiple strategies can be used, each with their own pros and cons. See related post: Advantages of implementing CI/CD environments at GAE project/app level vs service/module level?
But Cloud Functions do not have a versioning info associated with them (at least not yet), so deploying a different version of a function using the same name will overwrite the previous deployed version. So using different projects is your only option in this case.
Another theoretically possible approach would be to encode the environment/versioning info into the function name, which would also allow functions deployed from different environments to co-exist, but IMHO that would be an unnecessary complication.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I am investigating source control systems and considering migrating from SVN to either GIT or PlasticSCM. However to consider the costs, I'd like to know how much PlasticSCM will cost for us.
On their website they mention the community edition is free for up to 15 persons per team. However the definition of team is unclear for me: Is it usual in PlasticSCM to create a new repository per project? Or is the 15-person limit valid for all projects that use the same server?
Or in short: Can the community edition be used for two different repositories with 10 people using each?
The license model of PlasticSCM is per-user and per-server.
When a user performs a writable operation in the PlasticSCM server, a license (site) is used. The community edition can be used up to 15 users.
You can have all repositories you want, but you must manage less that 15 users, for each server.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm interested in Mule ESB but I dont understand the licence, could someone explan me the CPAL licence in simple words?
We have a commercial porduct (JavaEE web application) that neads to be integrated with solutions that are hosting in the cliens environment. For example a clienat has a SAP instalation or any other source of data and want to integrate it with our java web application. We woud like to Mule to achive this functionality, does the CPAL licence allow this?
Our application and Mule could be hosting on our internal machinery or at the clients, both ways are possible.
First: I do not know anything about law.
That said, the CPAL license is based on Mozilla Public License, which is less strict than GPL and you can mix license rather freely as long as the code stays open.
CPAL introduces a concept, that if you run your application with CPAL code in it (Mule for instance), as a "Cloud" service, then you will have to give out the code as well. Simply put, if you alter the Mule source code and host it as a cloud service, you will have to give out your modifications.
I really recommend you to talk to a lawyer in your area (which knows the local laws and immaterial laws etc). However, I do know about a few companies that "bundles" Mule CE with commercial products without concern for license issues in a way very similar to your situation.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
We are currently in the process of solidifying a database change management process.
We run MySql 5 running on RedHat 5. I have selected LiquiBase as the tool because it's open source and allows us to expand its functionality later if needed. It also seems to be one of the few free projects that are still active. Has anyone here had any experience using LiquiBase or other Db versioning tools?
Company Background: We are an SaaS company providing a 7/24 hosted application. There are dozens of instances running different versions of the same database and we need a way to manage the deploy process as it's starting to get out of control. The databases have hundreds of tables and we typically do releases once every 3 months.
I may be biased since I started LiquiBase, but I have been using it in production environments for several years and there have been many, many times where releases would have been a nightmare without it. LiquiBase has evolved to be very flexible and powerful and I have not ran into a situation that it was not able to handle (in one way or another) for quite some time.
The last code release contained of a project I am working on using LiquiBase contained a major database refactoring with hundreds of database changes and needed to be applied to a variety of installations that had different starting points for the database. When we did the release, the databases updated without any problems.
Doctrine, a PHP ORM/DBAL offers Migrations, doing what you want.
The Doctrine migration package allows
you to easily update your production
databases through a nice programmatic
interface. The changes are done in a
way so that your database is versioned
and you can walk backwards and
forwards through the database
versions.