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.

Sign up for GitHub

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

Jump to bottom

Update Component Service Configuration Steps #1265

Closed
ghost opened this issue Dec 18, 2017 · 0 comments · Fixed by #1300
Closed

Update Component Service Configuration Steps #1265

ghost opened this issue Dec 18, 2017 · 0 comments · Fixed by #1300
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers
Milestone
Sprint 24 Lifecycle

Comments

@ghost
Copy link

ghost commented Dec 18, 2017 •
edited by ghost
Loading

User Statement:

As a developer VIC Appliance component, I only want to write one systemd unit for configuring and starting my component service. This is in line with the component reference design documentation.

Details:
Fileserver, Harbor, and Admiral current have separate systemd units for configuration and startup of their component service's.

Acceptance Criteria:
Fileserver, Harbor, and Admiral have a single systemd unit with configuration steps in the ExecStartPre section of a simple unit.
@ghost ghost self-assigned this Dec 18, 2017
@ghost ghost added product/ova Related to the OVA packaging of vSphere Integrated Containers kind/enhancement Behavior that was intended, but we want to make better kind/quality labels Dec 18, 2017
@ghost ghost added this to the Sprint 23 Lifecycle milestone Dec 18, 2017
@ghost ghost mentioned this issue Dec 18, 2017
Closed
@ghost ghost mentioned this issue Jan 9, 2018
Merged
@ghost ghost modified the milestones: Sprint 23 Lifecycle, Sprint 24 Lifecycle Jan 10, 2018
@ghost ghost closed this as completed in #1300 Jan 17, 2018
ghost pushed a commit that referenced this issue Jan 17, 2018
Appliance systemd overhaul (#1300)
c646368 
Make a variety of changes to the systemd configuration of
the vic-product appliance, including:
 - Improved serviceability and linear boot dependencies.
 - A new custom boot target and new target for psc config.
 - Adds a psc reconfiguration target accommodating changes in
   system configuration over time.
 - Improved adherence to systemd best practices.
Fixes #1215, #1265, and #1267.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Behavior that was intended, but we want to make better product/ova Related to the OVA packaging of vSphere Integrated Containers
Projects
None yet
Milestone
Sprint 24 Lifecycle
Development

Successfully merging a pull request may close this issue.

Appliance systemd overhaul
[WIP] Appliance systemd overhaul
0 participants