Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capsules: Implement parent-side (satellite) prerequisites for setting up external capsule #185

Closed
cswiii opened this issue May 28, 2015 · 0 comments · Fixed by #233
Closed
Assignees

Comments

@cswiii
Copy link
Contributor

cswiii commented May 28, 2015

Complement to #186

In preparation for being able to automate capsule installation/configuration, there are bits that need to be done on the satellite side of the house. There may or may not be some of this in automation-tools already; if there are, we'll simply need to be able to tweak params.

REQUIREMENTS

  • Ability to install multiple capsules in serial or parallel
  • Ability to sync multiple capsules in serial or parallel (preferably async)
  • Ability to halt process if something goes wrong (i.e., sync not triggered if a capsule install/configuration fails)

Steps

  • sync capsule content
  • create content view with RHEL+Tools+capsule (RHEL7)
  • publish/promote content view
  • create activation key associated with content view
  • generate capsule cert

Proposed automation-tools namespace [and possible parameters/inputs]

  • capsule_sync [URL_for_capsule_content]
  • capsule_create_cv
  • capsule_publish_cv
  • capsule_ak_create
  • capsule_generate_cert
elyezer added a commit to elyezer/automation-tools that referenced this issue Aug 27, 2015
elyezer added a commit to elyezer/automation-tools that referenced this issue Aug 27, 2015
elyezer added a commit to elyezer/automation-tools that referenced this issue Aug 30, 2015
The capsule module contains helper tasks in order to accomplish the
capsule registering automation. They rely on a json configuration and
expect some data to be synced and set on Satellite before running it.

This is basically katello-rapid node migrated to be used inside
automation-tools.

Close SatelliteQE#185 and close SatelliteQE#186.
elyezer added a commit to elyezer/automation-tools that referenced this issue Sep 1, 2015
The capsule module contains helper tasks in order to accomplish the
capsule registering automation. They rely on a json configuration and
expect some data to be synced and set on Satellite before running it.

This is basically katello-rapid node migrated to be used inside
automation-tools.

Close SatelliteQE#185 and close SatelliteQE#186.
elyezer added a commit to elyezer/automation-tools that referenced this issue Sep 1, 2015
The capsule module contains helper tasks in order to accomplish the
capsule registering automation. They rely on a json configuration and
expect some data to be synced and set on Satellite before running it.

This is basically katello-rapid node migrated to be used inside
automation-tools.

Close SatelliteQE#185 and close SatelliteQE#186.
@elyezer elyezer self-assigned this Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants