Skip to content
Snippets Groups Projects
  1. Jun 03, 2017
    • Dai Dang Van's avatar
      Mixing binary and source images for I* and K* projects · bf0bf043
      Dai Dang Van authored
      In case Kolla's users want to deploy with both of
      binary and source image, we should have a variable
      install type that define install type for each project.
      
      We also add specific image tag for each Openstack project.
      
      This commit is implemented for Ironic, Kabor,
      Keystone project and iscsi as well.
      
      Change-Id: I134d840b1c0e24171a32dec0c7daa6dc2e9ecd87
      Implements: blueprint mixing-binary-and-source-image
      bf0bf043
  2. Jan 26, 2017
  3. Jan 20, 2017
  4. May 13, 2016
  5. Mar 09, 2016
  6. Mar 03, 2016
    • SamYaple's avatar
      Fix Keystone v3 and Horizon · 57124620
      SamYaple authored
      After our switch to keystone-manage bootstrap Horizon is not happy
      due to v3 not being setup correctly. This patch fixes that
      
      This also includes removal of unused variables (transforms them into
      endpoint url variables)
      
      TrivialFix
      Change-Id: I1e04db8c24049f80e974c063f03068a2ab32a563
      57124620
  7. Feb 29, 2016
  8. Feb 26, 2016
    • SamYaple's avatar
      Change kolla_internal_address variable · d3cfb205
      SamYaple authored
      Due to poor planning on our variable names we have a situation where
      we have "internal_address" which must be a VIP, but "external_address"
      which should be a DNS name. Now with two vips "external_vip_address"
      is a new variable.
      
      This corrects that issue by deprecating kolla_internal_address and
      replacing it with 4 nicely named variables.
      
      kolla_internal_vip_address
      kolla_internal_fqdn
      kolla_external_vip_address
      kolla_external_fqdn
      
      The default behaviour will remain the same, and the way the variable
      inheritance is setup the kolla_internal_address variable can still be
      set in globals.yml and propogate out to these 4 new variables like it
      normally would, but all reference to kolla_internal_address has been
      completely removed.
      
      Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
      Partially-Implements: blueprint ssl-kolla
      d3cfb205
  9. Feb 15, 2016
  10. Jan 20, 2016
  11. Sep 28, 2015
    • Jeff Peeler's avatar
      Add Ansible support for Ironic · f5a50a1d
      Jeff Peeler authored
      Configuration based off upstream documentation here:
      http://docs.openstack.org/developer/ironic/deploy/install-guide.html
      
      A few notes:
      -ironic-api is not configured to use mod_wsgi
      -several places it's noted that discoverd is going away and needs to be
      replaced with ironic-inspector - (sqlite connection should be changed
      too)
      -currently enabling ironic reconfigures nova compute (driver and
      scheduler) as well as changes neutron network settings
      -a nice enhancement would be to configure the web console
      
      Required post-deployment configuration:
      
      Create the flat network to launch the instances:
      
      neutron net-create --tenant-id $TENANT_ID sharednet1 --shared \
      --provider:network_type flat --provider:physical_network physnet1
      
      neutron subnet-create sharednet1 $NETWORK_CIDR --name $SUBNET_NAME \
      --ip-version=4 --gateway=$GATEWAY_IP --allocation-pool \
      start=$START_IP,end=$END_IP --enable-dhcp
      
      And then the above ID is used to set cleaning_network_uuid in the neutron
      section of ironic.conf.
      
      Change-Id: I572e7ff1f23c4e57a2c50817cafe9269fd9950dd
      Implements: blueprint ironic-container
      f5a50a1d
Loading