summaryrefslogtreecommitdiffstats
path: root/docs/development/gapanalysis/index.rst
blob: d29cea32ec4ec093d05ff5af67c762cafa5ca9d7 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License. http://creativecommons.org/licenses/by/4.0
.. (c) Xuan Jia (China Mobile), Gergely Csatari (Nokia)

==========================
OpenRetriever Gap Analysis
==========================

:Project: OpenRetriever, https://wiki.opnfv.org/display/openretriever

:Editors: Xuan Jia (China Mobile)
:Authors: Xuan Jia (China Mobile)

:Abstract: This document provides the users with top-down gap analysis regarding
           OpenRetriever feature requirements with OPNFV Installer, OpenStack
           Official Release and Kubernetes Official Release.

.. toctree::
   :maxdepth: 2

   gap-analysis-architecture-options
   gap-analysis-opnfv-installer.rst
   gap-analysis-openstack.rst
   gap-analysis-kubernetes-v1.5.rst
-Indicator">{get_resource: user_config} - config: {get_resource: ssh_config} # Get cloud-init to create an extra user, in addition to the default for the # distro. Note there are various options, including configuring ssh keys, # but atm I can only see how to specify the keys explicitly, not via metadata user_config: type: OS::Heat::CloudConfig properties: cloud_config: users: - default - name: {get_param: extra_username} # Setup ssh key for the extra user to match the key installed for the default # user, e.g that provided via the nova keypair on instance boot ssh_config: type: OS::Heat::SoftwareConfig properties: config: str_replace: template: | #!/bin/bash curl http://169.254.169.254/openstack/2012-08-10/meta_data.json -o /root/meta_data.json mkdir -p /home/$user/.ssh chmod 700 /home/$user/.ssh cat /root/meta_data.json | jq -r ".keys[0].data" > /home/$user/.ssh/authorized_keys chmod 600 /home/$user/.ssh/authorized_keys chown -R $user:$user /home/$user/.ssh params: $user: {get_param: extra_username} outputs: # This means get_resource from the parent template will get the userdata, see: # http://docs.openstack.org/developer/heat/template_guide/composition.html#making-your-template-resource-more-transparent # Note this is new-for-kilo, an alternative is returning a value then using # get_attr in the parent template instead. OS::stack_id: value: {get_resource: userdata}