I took a look at this experiment just now. The correct passwd hash for
the root account is in the image, and it is a valid hash of the default
passwd for the profile. The profile setup scripts leave the raw image
file in /root/setup after uploading it into Glance.
I can't use the console to try to login to your existing instance,
because you're on the Cloudlab Utah (aarch64) cluster, which doesn't yet
support a graphical console for VMs. And the "new serial support"
option wasn't selected, so serial console access is not available. So
all we have is the VM serial console logfiles.
I created an instance on the flat network, and was able to ssh as root
using the default passwd from the 'ctl' physical host, no problems. (I
had to ssh from the ctl node because it has access to the default flat
network, and your two instance VMs had already used the 2 spare public
IP addresses the profile allocates by default.) I can't ping your VMs
either. You associated them with the 'ext' network directly, and that's
not a configuration we support (if you check the console logs, the VM
doesn't receive an IP address on its NIC, so it's unsurprising that ping
doesn't work -- so I'm also a bit confused about how you were able to
try to login...). The 'ext' network is there to host floating IPs... so
the supported use case would be to associate your instance VMs with
either the 'tun0' network, or the flat network, and then bind floating
IP addrs to your VMs as needed.
Hope this helps...
David
On 09/22/15 12:35, Mark Coatsworth wrote:
> I've already tried with both root and ubuntu (and just tried again to
> make sure). Neither work with that password, with or without the private
> key.
>
> Any ideas what might be causing this?
>
>
> On Tuesday, September 22, 2015 at 9:16:47 AM UTC-5, Aaron
> Gember-Jacobson wrote:
>
> Actually, try the user 'root' and the same password.
>
> On Tue, Sep 22, 2015 at 8:55 AM, Gember-Jacobson, Aaron
> <
aa...@gemberdesign.com <javascript:>> wrote:
>
> Try logging in as the user ubuntu with the password N!ceD3m0
> (the default admin password for the OpenStack profile).
>
> Aaron
>
> On Sep 21, 2015 5:00 PM, "Mark Coatsworth" <
mark.co...@gmail.com
> <javascript:>> wrote:
>
> I've got an OpenStack topology with a VM instance exposed to
> the public internet. I'm trying to log in to this instance
> using ssh. According to the Profile Instructions:
>
> "Please visit the OpenStack controller WWW interface once
> your experiment boots (approx. 5-10 minutes). Log in as
> admin with the password you chose. This same password can be
> used to log in as root to VM instances you bring up."
>
> However this doesn't quite work. The password I chose works
> fine for the admin WWW interface. But I can't use it to ssh
> in to my VM; the connection is fine it says the password is
> wrong. I've tried under a variety of usernames (root,
> ubuntu, my cloudlab username). Tried using a .pem key as
> well. Still no luck.
>
> Does anybody know how to log in?
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
cloudlab-user...@googlegroups.com
> <javascript:>.
> To post to this group, send email to
>
cloudla...@googlegroups.com <javascript:>.
> <
https://groups.google.com/d/msgid/cloudlab-users/9dcd8d00-1e6d-49f5-a4ec-0a167d45f999%40googlegroups.com?utm_medium=email&utm_source=footer>.
> <
https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
cloudlab-user...@googlegroups.com
> <mailto:
cloudlab-user...@googlegroups.com>.
> <mailto:
cloudla...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/cloudlab-users/4cebda00-07f9-449c-bd16-56218c674d05%40googlegroups.com
> <
https://groups.google.com/d/msgid/cloudlab-users/4cebda00-07f9-449c-bd16-56218c674d05%40googlegroups.com?utm_medium=email&utm_source=footer>.