1. 25 Feb, 2016 1 commit
  2. 17 Feb, 2016 1 commit
  3. 01 Feb, 2016 1 commit
    • David Johnson's avatar
      Use a less lame swapper == geniuser check. · 8a8fa109
      David Johnson authored
      If you instantiate a portal expt on Emulab (where you might have a real
      account), the swapper is you, not geniuser.  So, check geniuser via
      geni-get slice_urn success/failure.
      8a8fa109
  4. 03 Sep, 2015 1 commit
  5. 30 Jul, 2015 2 commits
    • David Johnson's avatar
      86bb9e67
    • David Johnson's avatar
      Make sure openstack special IPs don't stomp on our flat lan phys IPs. · c2676e3a
      David Johnson authored
      For our flat lan case, we run lans directly over the top of real (or
      emulab vlan) networks.  So we extend those emulab IP networks into
      the openstack flat network associated with each emulab network.  Well,
      openstack assumes it controls the subnet and can just allocate special
      addresses anywhere -- like for the local dhcp agent IP, or a router
      interface -- it doesn't respect the allocation_pool value we give the
      network (so that must just be for compute nodes).
      
      Further, there's no way to set these special IPs when creating networks,
      subnets, and routers, so we retroactively find those ports and change
      their IP addrs to something that won't stomp on emulab IPs, nor on the
      openstack allocation_pool.
      
      This seems to work great, except that packets outbound from an openstack
      instance don't get SNAT'd so they appear they came from the real
      external world address.  Inbound packets make it all the way, so at
      least DNAT is working.
      c2676e3a
  6. 28 Jul, 2015 1 commit
  7. 16 Jul, 2015 1 commit
    • David Johnson's avatar
      Lots of new features, especially drastically improved network config. · a9265ea7
      David Johnson authored
      Setup several kinds of networks: tunnels, flat networks, flat networks
      multiplexed via vlans over physical networks (where openstack doesn't
      manage the vlan ids), and real vlan networks (where openstack *does*
      manage the vlan ids).  Tunnels always go over the first flat data net.
      
      Be very flexible in terms of assigning IPs; generate them ourselves
      if they dind't come to us, or if user wants to use our generated ones.
      I tried to be smart (enough) with this.
      
      Setup VNC-based consoles on x86-64; working in dashboard.
      
      Don't put plaintext admin password in profile anymore; instead, expect
      a hash of the admin password.  Replace the temp admin password in the
      keystone database with the hash we get.  But, since the CLI tools
      all require real user auth, setup a secondary 'adminapi' account
      that is a real admin, and use that to see admin-openrc.sh for CLI
      tools, and for all our configuration, and places where the services
      use a real admin account to auth.  Also, push the admin password
      hash all the way into our instance images.
      a9265ea7
  8. 22 Apr, 2015 1 commit
  9. 18 Apr, 2015 1 commit
  10. 20 Mar, 2015 1 commit
  11. 18 Mar, 2015 1 commit
    • David Johnson's avatar
      Tweak the network setup config so it's right. · 0c32c3b0
      David Johnson authored
      And also, don't add extra network public gateways via
      ext-net if there aren't enough public IPs.  We need at
      least 2 so that there is 1 floater and 1 for the private-to-public
      router interface :(
      0c32c3b0
  12. 17 Mar, 2015 1 commit
  13. 13 Mar, 2015 5 commits