On Mon, Oct 22, 2012 at 12:09 PM, Aaron Peeler <[email protected]> wrote: > Hi Curtis, > > The process flow is not documented, but yes when a user hits the > connect button the OS firewall is modified. But looking at your log > output, it's not getting to that step.
Ok, I think you are right. I think it was just coincidence that the networking failed when I clicked connect. I did a few more tests and waited longer and the networking for the instance is failing. I think I've hit a known OpenStack bug that is fixed in updates, so I will try that out. Thanks for your help, Curtis. > > It's not able to ssh into the vm1 to update anything. > > Can to tell if anything is happening to vm1 between the new state and > the reserved state? > Like the vm1 gets turned off or the vm gets a new IP from openstack > and is does not resolve to vm1 anymore? > > Aaron > > On Mon, Oct 22, 2012 at 12:50 PM, Curtis C. <[email protected]> wrote: >> Hi, >> >> I have a Windows server 2008 instance/slot/computer which is up until >> the user connects, then the networking on the instance stops, I assume >> because hitting the connect button sets off some kind of networking >> process on the instance, such as adding firewall rules. In this case >> the instances get their IP via DHCP because VCL is being backended by >> OpenStack. >> >> Is that connection/networking process documented anywhere? >> >> As I may be totally wrong, kinda new to VCL :), about what is going >> on, here are the logs for one of the reservations: >> >> http://pastebin.com/raw.php?i=L5G3qCmx >> >> Thanks, >> Curtis. >> >> -- >> Twitter: @serverascode >> Blog: serverascode.com > > > > -- > Aaron Peeler > Program Manager > Virtual Computing Lab > NC State University > > All electronic mail messages in connection with State business which > are sent to or received by this account are subject to the NC Public > Records Law and may be disclosed to third parties. -- Twitter: @serverascode Blog: serverascode.com
