Sun, Jun 17
Fri, Jun 15
http://wikistream.wmflabs.org/ seems up, for the moment at least.
Wed, Jun 13
I just changed the glance endpoints on labtestn so that they're the same as for labtest:
Tue, Jun 12
Mon, Jun 11
@aborrero, thanks for investigating. I'm sure that that the existing client_pinning file isn't complete, and that making it complete for use on all our servers will be very messy :/
I don't mind having to manually fix some puppetmasters, although it would be nice to do them all at once :) I'll try cherry-picking a few of these changes and see if I can get a sense of what's likely to break.
This is looking like it's outside my area of influence so I'm unassigning myself.
@aborrero doesn't pinning work if we pin the keystone package and all dependencies? Like in openstack::jessie_mitaka_client_pinning ?
Fri, Jun 8
The remaining issue is a stray process that gets created but not cleaned up by the puppetization process:
Hm, I rebooted the master and now everything works. So I think we're basically good, minus one apparent race condition.
It definitely doesn't work easily -- I'm getting puppet failures right out of the gate. So, please don't close yet.
I see this, and it's obviously wrong (unless that number is some internal ID that means something to the API, in which case it's just very user-unfriendly.)
I just tried and it worked for me. Can you tell me what project/instance you're seeing this with?
Can you tell me more about that -X? X11 isn't present on any of our servers by default, I don't think I've ever heard of anyone using it on a VPS before.
Thu, Jun 7
(previously, https://phabricator.wikimedia.org/T193651 )
andrew@labcontrol1001:~$ openstack role list +----------------------------------+----------------+ | ID | Name | +----------------------------------+----------------+ | 1102f4ff63c3435793d0e4340bf4b04e | glanceadmin | | 2cd63d467f754404bf3746fe63ee0698 | admin | | 47a8370618ea42d49f7047774e75d262 | observer | | 4d8cad783d6342efa8414d7d36fbc034 | projectadmin | | 906f1588626d4d0993629ea3928b6fb4 | designateadmin | | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | | f473273fac7146b3bdbf22e5d4504f95 | user | +----------------------------------+----------------+ andrew@labcontrol1001:~$ openstack role assignment list | grep deployment-prep-dns-manager | 47a8370618ea42d49f7047774e75d262 | deployment-prep-dns-manager | | deployment-prep | | False | | 906f1588626d4d0993629ea3928b6fb4 | deployment-prep-dns-manager | | deployment-prep | | False |
I've issued deployment-prep-dns-manager the designateadmin role on deployment-prep.
I'm going to create a new role, 'designatemanager' and attach a patch here granting some DNS privs to that role. Then I think we should create a new user and give it 'observer' and 'designatemanager' on deployment-prep.
Wed, Jun 6
I doubt that there's any interaction between the two accounts (mech vs. smccandlish) and there's definitely no interaction between the wikitech account and the SUL account.
Tue, Jun 5
Done. Thank you for giving attention to this project!
Mon, Jun 4
Can this wait a few days?
Sorry, @Cmjohnson, to be clear I was asking if you've already replaced the paste on this server, not saying that I think you have.
In the past I've reapplied thermal paste. Let me know if you would like to schedule a time to do that.
Sun, Jun 3
Fri, Jun 1
... I suppose another option is to leave OpenStackManager in place but unused apart for user creation, until we make wikitech SUL and move all developer account creation to Striker.
@bd808, does striker not already do all the necessary things to create an account? Or is that accomplished via a wikitech hook?
I've removed all of Wikitech's sidebar links to OSM. If we avoid protest and surprise for a few weeks I'll rip out the code.
Wed, May 30
Looks fixed to me
@Krenair confirms that this is now fixed
Fri, May 25
May 17 2018
Looks good! Thanks @Cmjohnson
May 16 2018
@Cmjohnson, all set for you to move labnet1002 now.
May 15 2018
@Manducus, the project now exists. You can add other users and projectadmins as you see fit.
@Manducus, I can't find your wikitech/developer account -- do you have a developer account? If so, what is your user name?
We're approving this request (with standard quotas) for you to test and set up a prototype. Keep in mind that any full-scale implementation (e.g. all images on Commons or something like that) will require quite a bit more discussion regarding bandwidth and distributed object stores and other complications :)
This is mysterious, but resolved for now.
I rebooted it and repooled it. There's nothing useful in the syslog, just a long silence:
May 14 2018
I'm just checking in -- can this VM be deleted yet?
OK. In theory we can move it after the outage window tomorrow, since we're planning to switch all traffic back to labnet1001 after it gets re-racked. The only risk I can think of is if labnet1001 doesn't survive the move and we have to rely on 1002 long-term.
May 12 2018
@Nehajha Something like that would be just fine. I might suggest that you keep the output limited to one line so it's a bit easier for automatic jobs to parse or grep. Maybe just 'Your webservice of type xxx is running.'
May 11 2018
@fgiunchedi Can you comment on what this alert might mean?
I'm deleting pdfservice, swproxy, zotero-test citoif-test citoid-jessie-test and sca1. Appservice remains.
May 10 2018
I'm flying on the 29th. If Chase wants to manage these things without me that's fine with me though :)
In theory we can do it on the 24th but the 31st is much better for me.
May 9 2018
May 8 2018
I haven't implemented paging. That means that in the Tools project, loading the page and interacting with it is pretty slow. Since most of this functionality is now handled by Striker I'm not sure it's worth implementing paging in this panel -- as best I can tell it's perfectly responsive for all other projects.
May 2 2018
I've confirmed that VMs on labtestvirt2002 work properly. Thank you!
@Cmjohnson, The 15th sounds good for labnet1001. I don't think 1500UTC is the same thing as 1000 EST but I'm going to assume that the EST part is what interests you :)
@Cmjohnson, sorry, now we're talking about doing this all in one day. Could you be available for a specific appointment (probably around 1PM) to re-rack this box on either Friday May 11th or Tuesday May 15th? The 15th is mildly better but if either one works for you that'd be great.
May 1 2018
@Cmjohnson, I propose to fail over to labnet1002 on May 8th (Tuesday) and switch back to 1001 on May 15th (also a Tuesday). Can you commit to re-racking labnet1001 sometime on Wednesday, Thursday or Friday next week?
root@labnet1002:~# uname -a Linux labnet1002 3.13.0-145-generic #194-Ubuntu SMP Thu Apr 5 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
@zhuyifei1999 are you still blocked by this?
I think this is under control now. I've opened T193272 about the misreporting issue.