On 03/25/2015 02:40 AM, Kevin Fenzi wrote: >> > The login here doesn't actually work for me in the new cloud; is it >> > expected to, or were new passwords allocated? > These were new randomly generated passwords. I can send you that one, > but... see below. This is kind of tricky. I have to first set a password for new user. So I can then upload his SSH key. Then Kevin or somebody else have to tell you that password so you can log in and change it. In OpenStack Kilo will be "Forgoten password" feature, where you will be able to reset it yourself. However that is far feature for us. >> > I'd like to use instances in the cloud for status reporting of tasks >> > from the current atomic01.qa machine, and move off the deprecated >> > fed-cloud02. > Thats great, but the new cloud is not yet done. It's not open for > business. ;) We are going to reinstall it at least one more time > before we put it in service. So, I can send you info, but you should > realize any instances you make can and will be completely vaporized > when we reinstall, and possibly could break when we try and fix > something else. > >> > I'm not sure if anyone else was using the old cockpit tenant anymore; >> > I briefly repurposed it for rpm-ostree work. So perhaps the right >> > thing here is to request a new "atomic" tenant. > Sure, we could rename... makes sense, but we can do that when we > reinstall more likely. OK. I will rename it to atomic in playbook. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
