NIC templates examples for usual custom roles
Bug #1625558 reported by
Marius Cornea
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dan Sneddon |
Bug Description
We should add some NIC template examples showing which networks are required for usual custom roles such as: networker node running neutron agents, controller node running the pacemaker managed services, service api nodes running the openstack api services.
Changed in tripleo: | |
milestone: | newton-rc2 → ocata-1 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-1 → newton-rc3 |
Changed in tripleo: | |
milestone: | ocata-1 → none |
Changed in tripleo: | |
assignee: | Steven Hardy (shardy) → Dan Sneddon (dsneddon) |
status: | Invalid → In Progress |
Changed in tripleo: | |
milestone: | none → pike-1 |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Thanks for the bug report, can you provide a little more detail about what you'd like to see as the fix here?
I've been working on a script which basically creates a skeleton environment like:
OS::TripleO::Foo: foo-templates/ foo.yaml :FooConfig: foo-templates/ foo-config. yaml :Foo::Net: :SoftwareConfig : ../net- config- noop.yaml :Foo::Ports: :ExternalPort: ../network/ ports/noop. yaml :Foo::Ports: :InternalApiPor t: ../network/ ports/noop. yaml :Foo::Ports: :StoragePort: ../network/ ports/noop. yaml :Foo::Ports: :StorageMgmtPor t: ../network/ ports/noop. yaml :Foo::Ports: :TenantPort: ../network/ ports/noop. yaml :Foo::Ports: :ManagementPort : ../network/ ports/noop. yaml
OS::TripleO:
OS::TripleO:
# Port assignments for the Foo role
OS::TripleO:
OS::TripleO:
OS::TripleO:
OS::TripleO:
OS::TripleO:
OS::TripleO:
This can then easily be customized in the same way as any other role, but I'm not sure we need to provide custom-role specific examples? (or do we?) I'd assumed folks would simply apply their preferred ports and network config based on knowledge of their existing non-custom roles?