Suggession on managing operating system contents ( cvs )

Support
1

Hello,

we have 2 separate depts, Unix engineering and Unix operations, unix
engineering is responsible for testing OS provisioining and developing
puppet modules and defining final operating system build,

Now Unix operations take over this build and start provisioning and support.

Do we have any way in katello so Unix engineering can develop build in
their katello instance and later Unix operations can sync directly from
their ? ( rather then following all steps again )

we can have Life cycle env like engineering -> dev -> stage -> prod, but
issue is, as per policy engineering can not touch production instance and
they have to work in engineering instance.

can anyone suggest best approach to achieve this ?

Regards,
DJ

2

You could create two completely separate Lifecycle Environment chains? One
for Engineering to do their thing, the other for the more general

ยทยทยท >>Prod cycle for Ops to keep the show on the road.

On Wednesday, 2 December 2015 16:15:22 UTC, Unix SA wrote:

Hello,

we have 2 separate depts, Unix engineering and Unix operations, unix
engineering is responsible for testing OS provisioining and developing
puppet modules and defining final operating system build,

Now Unix operations take over this build and start provisioning and
support.

Do we have any way in katello so Unix engineering can develop build in
their katello instance and later Unix operations can sync directly from
their ? ( rather then following all steps again )

we can have Life cycle env like engineering -> dev -> stage -> prod, but
issue is, as per policy engineering can not touch production instance and
they have to work in engineering instance.

can anyone suggest best approach to achieve this ?

Regards,
DJ

3

As i already mention, engineering is not allowed to touch to production katello, even with different lifecycle env, it must be separate instance.

Also, if i create diff env( which will not be possible in my case) is it possible to update puppet classes on env basis?? Engineering and ops has to modify same puppet class and if engineering puts something for testing and that breaks production will create impact.

I am looking for suggestion where i have 2 katello instances and if i update engineering, create cv, puppet class and once i lock, migrate it to prod instance.

Regards,
DJ