In these days I’m working several hours with Redhat Satellite 6.2.9
The architecture is composited by:
1x satellite orchestrator
6x capsules
I made a new lifecycle/content view/activation keys objects and I need on a capsule to sync it for a specific lifecycle, instead of syncing it for *all* lifecycles assigned.
I was very funny to explore hammer CLI options:
[root@lsatellite ~]# hammer capsule list
—|————————————|————————————————-|————————–
ID | NAME | URL | FEATURES
—|————————————|————————————————-|————————–
2 | lxrp-capsule-area3.pippo.net | https://lxrp-capsule-area3.pippo.net:9090 | Templates, Pulp Node, …
7 | lxrp-capsule-ca4p1.pippo.net | https://lxrp-capsule-ca4p1.pippo.net:9090 | Templates, Pulp Node, …
3 | lxrp-capsule-dcs.pippo.net | https://lxrp-capsule-dcs.pippo.net:9090 | Templates, Pulp Node, …
4 | lxrp-capsule-ibi.pippo.net | https://lxrp-capsule-ibi.pippo.net:9090 | Templates, Pulp Node, …
5 | lxrp-capsule-itzrm.pippo.net | https://lxrp-capsule-itzrm.pippo.net:9090 | Templates, Pulp Node, …
6 | lxrp-capsule-visby.pippo.net | https://lxrp-capsule-visby.pippo.net:9090 | Templates, Pulp Node, …
1 | lxrp-ltm-satellite.pippo.net | https://lxrp-ltm-satellite.pippo.net:9090 | Pulp, Puppet, Puppet C…
—|————————————|————————————————-|————————–
[root@satellite ~]# hammer lifecycle-environment list –organization XXX
—|———————|——————-
ID | NAME | PRIOR
—|———————|——————-
9 | VcloudIrector | Library
4 | Test | development
22 | reference-snapshot | Library
23 | reference-release | reference-snapshot
2 | Production | Library
7 | Library-2 | Library
1 | Library |
3 | development | Production
10 | Content_Jenkins | Library
8 | Base-release-upload | Library-2
—|———————|——————-
[root@satellite ~]# hammer capsule content synchronize –id 7 –environment-id 22 –organization GTK
[………………………………………………………………………………………………………………………………………… ] [80%]
[………………………………………………………………………………………………………………………………………… ] [80%]
[………………………………………………………………………………………………………………………………………… ] [80%]
Done!!! 🙂