[Bug 1429862] Re: Spinning nova testbeds in given security-groups

[Launchpad Bug Tracker]

This bug was fixed in the package autopkgtest - 3.12

---------------
autopkgtest (3.12) unstable; urgency=medium


  * ssh-setup/adb: Re-enable ssh after reboot, in case an upgrade disables it.
  * ssh-setup/adb: Try to create /userdata/.adb_onlock, to get adb after
    rebooting without human interaction.
  * Fix apt-get install --simulate version parsing with third-party sources.
    (LP: #1430017)
  * ssh-setup-nova: Add --security-groups option. (LP: #1429862)
  * adt-buildvm-ubuntu-cloud: Avoid non-blocking reads from the socket in
    verbose mode, this sometimes causes hangs. Go back to blocking reads, but
    don't wait between them.
  * Fix UnicodeDecodeError on .deb package name reading. (LP: #1430773)
  * adt-virt-ssh: Export $SUDO_ASKPASS to tests if sudo is available.
    (LP: #1431421)

 -- Martin Pitt <mpitt at debian.org>  Fri, 13 Mar 2015 12:52:49 +0100

** Changed in: autopkgtest (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1429862

Title:
  Spinning nova testbeds in given security-groups

Status in autopkgtest package in Ubuntu:
  Fix Released

Bug description:
  This is a feature request to the current nova-ssh setup support for
  having more secure testbeds  in wild cloud-environments.

  I am looking for a way to spin testbeds that are only accessible from
  an specific keypair (already supported by the --key-pair option) and
  has access restrictions defined by specifics security group, for
  instance:

  {{{
  nova boot ... --security-groups <testbed-0>
  }}}

  The 'testbed-0' security group would be created prior to the `adt-run`
  allowing only ssh connections from the host and possibly internet
  access (for pkgs which needs it). This way the testbed access to other
  testbeds or infrastructure components within the same cloud could be
  programatically restricted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1429862/+subscriptions