Salt keys will soon be the more reasonable <instance>.<project>.eqiad.wmflabs. monitor_labs_salt_keys.py needs to support that case as well as the old ec2-based case.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Andrew | T42525 Cant add a security group to an existing instance | |||
Resolved | Andrew | T87279 Make OpenStack Horizon useful for production labs | |||
Resolved | hashar | T96670 Instances created by Nodepool cant run puppet due to missing certificate | |||
Resolved | Andrew | T97163 Support instance creation/deletion via nova commandline | |||
Resolved | Andrew | T91987 Nova Instance creation hook for ldap | |||
Duplicate | Andrew | T95910 Abolish use of ec2 ids | |||
Resolved | Andrew | T95911 Remove puppet and salt keys on instance deletion | |||
Resolved | Andrew | T1154 Make labs salt use instance names than ids | |||
Resolved | Andrew | T95480 Abolish use of ec2id in cert names | |||
Resolved | ArielGlenn | T95481 Fix monitor_labs_salt_keys.py to handle the new labs naming scheme |
Event Timeline
Comment Actions
when you say instance, you mean the ec2 name there, right? or no? give me a sample name with all the pieces in it.
Comment Actions
Yes and no. I'm trying to eliminate use of the ec2 ID. So, for example, my instance util-abogott used to have a salt key of 'i-000000ee.eqiad.wmflabs'; now it uses 'i-000000ee.testlabs.eqiad.wmflabs' but soon it will just be 'util-abogott.testlabs.eqiad.wmflabs.'
That last change is pending https://gerrit.wikimedia.org/r/202924