This project is mirrored from https://:*****@osm.etsi.org/gerrit/osm/devops.git. Pull mirroring updated .
  1. Dec 02, 2019
  2. Nov 29, 2019
  3. Nov 28, 2019
  4. Nov 27, 2019
    • garciadeblas's avatar
      full_install_osm.sh: install python3-osmclient and IM dependencies · 078f5985
      garciadeblas authored
      
      
      Change-Id: I7e9d52cdb0ae350d229283f9910b194202a4ca2e
      Signed-off-by: default avatargarciadeblas <gerardo.garciadeblas@telefonica.com>
      078f5985
    • vijaynag's avatar
      Gerrit ID: 5665 - Deploys OSM on Kubernetes. · 8339ed24
      vijaynag authored and garciadeblas's avatar garciadeblas committed
      
      Run the installation script with -c k8s to deploy osm on K8s.
      To Uninstall OSM deployed on Kubernetes run script with --uninstall -c k8s.
      Each yaml file in osm_pods directory contains yaml definitions for pods and services.
      
      Added license to yaml files in osm_pods.
      
      Changed volume mounts to OSM_NAMESPACE_VOL from docker volumes.
      
      Removes all pods and services while uninstalling.
      
      Added namespace to deploy osm services. Deleting namespace
      for uninstalling osm services.
      Resolved Merge conflict with Change-7931. Changed Mongo, Kafka,
      zookeeper, mysql and prometheus to statefulset.
      
      -s <namespace> users can define namespace for k8s to deploy
      osm services.
      
      Added cluster configuration file which will be used to install k8s control plane
      Addressed nodeport range issue and resolved merge conflict.
      
      Added two yaml files to create a job for systest and robot test.
      
      Change-Id: Iabe70fa7aed9cd638011bb92e2f300e32cff5772
      Signed-off-by: default avatarvijaynag.bs <vijaynag.bs@tataelxsi.co.in>
      8339ed24
  5. Nov 25, 2019
  6. Nov 22, 2019
  7. Nov 06, 2019
  8. Oct 25, 2019
  9. Oct 16, 2019
  10. Oct 03, 2019
    • israelad's avatar
      Native charm support · 5ddc97f9
      israelad authored
      
      
      This commit adds an API Proxy env variable to __lcm__.env, in order to
      enable native charm support in OSM.
      
      The default behavior is to automatically detect the IP of the primary
      interface. This can be overridden with the -A flag.
      
      Change-Id: I172ce4f7bb76f67ae9fb8918cdd5a10c93fa3b8a
      Signed-off-by: default avatarAdam Israel <adam.israel@canonical.com>
      5ddc97f9
  11. Sep 10, 2019
  12. Sep 09, 2019
  13. Aug 09, 2019
    • israelad's avatar
      Fix bug 816 · 34f8b6bc
      israelad authored
      
      
      This pins the installed version of Juju to 2.5, which matches the pinned
      version of libjuju used by N2VC. The mismatch is causing issues
      deploying charms with new installs.
      
      Change-Id: Ia831b7735511172a64e6e691ce87848dc5b95ae4
      Signed-off-by: default avatarAdam Israel <adam.israel@canonical.com>
      34f8b6bc
  14. Aug 01, 2019
  15. Jun 26, 2019
  16. Jun 11, 2019
  17. May 30, 2019
    • beierl's avatar
      Fix Shell Command · 63229a28
      beierl authored
      
      
      Replaces 'source' with '.' as the command 'source' is not
      valid sh syntax.  It is only valid in bash, but the sg
      command invokes sh, not bash.
      
      BUG 717
      
      Change-Id: I76f58120cff78420a751308c283798ad57b83df8
      Signed-off-by: default avatarbeierl <mbeierl@vmware.com>
      63229a28
  18. May 29, 2019
  19. May 24, 2019
  20. May 22, 2019
  21. Apr 17, 2019
  22. Apr 08, 2019
  23. Apr 05, 2019
  24. Mar 01, 2019
    • diazb's avatar
      Modifies Keystone to use same MySQL DB as RO · 6e3a2b64
      diazb authored and diazb's avatar diazb committed
      
      
      ro-db is renamed to mysql
      
      There is no benefit of having multiple sql database engines. All components
      should share the same. This is part of the effort to make OSM components
      support an HA scenario. Unifying sql db engines, allows to have them all
      connected to a database cluster, for example.
      
      Change-Id: I5d0f2b75da9ea7c6bbb341cac3cb899b4821dd40
      Signed-off-by: default avatarBenjamin Diaz <bdiaz@whitestack.com>
      6e3a2b64
  25. Dec 13, 2018
  26. Dec 05, 2018
  27. Dec 04, 2018
  28. Dec 03, 2018
  29. Nov 30, 2018
  30. Nov 28, 2018
  31. Nov 27, 2018
  32. Nov 23, 2018
  33. Nov 22, 2018
    • israelad's avatar
      (bug 578) Fix installer on Ubuntu 18.04 · 8232e569
      israelad authored
      
      
      We originally ran into this at the hackfest, where the installer would
      fail on Ubuntu 18.04, the latest long-term supported release.
      
      The behaviour of the `sg` command has failed (an apparent upstream
      change) so that it can't be reliably used to check the error code of the
      command it runs.
      
      Considering the original use of `sg`, to ensure that the user had access
      to lxd in order to bootstrap, reduces how we use `sg`, only calling it
      if we need to bootstrap a new juju controller.
      
      The other commands -- `juju show-controller` and `juju controllers` --
      do not need access to the lxd group in order to function.
      
      I've tested this patch on Ubuntu 16.04 and 18.04 and verified that it
      works as expected on both (where lxd now pre-installed) and will also
      work with older versions of 16.04 that may not have it installed.
      
      Signed-off-by: default avatarAdam Israel <adam.israel@canonical.com>
      Change-Id: I0e50ef3ac3cf127b63f5f56d8f90fea44f5be0f2
      8232e569