1
0

oneandone.rst 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170
  1. ==========================
  2. Getting Started With 1and1
  3. ==========================
  4. 1&1 is one of the world’s leading Web hosting providers. 1&1 currently offers
  5. a wide range of Web hosting products, including email solutions and high-end
  6. servers in 10 different countries including Germany, Spain, Great Britain
  7. and the United States. From domains to 1&1 MyWebsite to eBusiness solutions
  8. like Cloud Hosting and Web servers for complex tasks, 1&1 is well placed to deliver
  9. a high quality service to its customers. All 1&1 products are hosted in
  10. 1&1‘s high-performance, green data centers in the USA and Europe.
  11. Dependencies
  12. ============
  13. * 1and1 >= 1.2.0
  14. Configuration
  15. =============
  16. * Using the new format, set up the cloud configuration at
  17. ``/etc/salt/cloud.providers`` or
  18. ``/etc/salt/cloud.providers.d/oneandone.conf``:
  19. .. code-block:: yaml
  20. my-oneandone-config:
  21. driver: oneandone
  22. # Set the location of the salt-master
  23. #
  24. minion:
  25. master: saltmaster.example.com
  26. # Configure oneandone authentication credentials
  27. #
  28. api_token: <api_token>
  29. ssh_private_key: /path/to/id_rsa
  30. ssh_public_key: /path/to/id_rsa.pub
  31. Authentication
  32. ==============
  33. The ``api_key`` is used for API authorization. This token can be obtained
  34. from the CloudPanel in the Management section below Users.
  35. Profiles
  36. ========
  37. Here is an example of a profile:
  38. .. code-block:: yaml
  39. oneandone_fixed_size:
  40. provider: my-oneandone-config
  41. description: Small instance size server
  42. fixed_instance_size: S
  43. appliance_id: 8E3BAA98E3DFD37857810E0288DD8FBA
  44. oneandone_custom_size:
  45. provider: my-oneandone-config
  46. description: Custom size server
  47. vcore: 2
  48. cores_per_processor: 2
  49. ram: 8
  50. appliance_id: 8E3BAA98E3DFD37857810E0288DD8FBA
  51. hdds:
  52. -
  53. is_main: true
  54. size: 20
  55. -
  56. is_main: false
  57. size: 20
  58. The following list explains some of the important properties.
  59. fixed_instance_size_id
  60. When creating a server, either ``fixed_instance_size_id`` or custom hardware params
  61. containing ``vcore``, ``cores_per_processor``, ``ram``, and ``hdds`` must be provided.
  62. Can be one of the IDs listed among the output of the following command:
  63. .. code-block:: bash
  64. salt-cloud --list-sizes oneandone
  65. vcore
  66. Total amount of processors.
  67. cores_per_processor
  68. Number of cores per processor.
  69. ram
  70. RAM memory size in GB.
  71. hdds
  72. Hard disks.
  73. appliance_id
  74. ID of the image that will be installed on server.
  75. Can be one of the IDs listed in the output of the following command:
  76. .. code-block:: bash
  77. salt-cloud --list-images oneandone
  78. datacenter_id
  79. ID of the datacenter where the server will be created.
  80. Can be one of the IDs listed in the output of the following command:
  81. .. code-block:: bash
  82. salt-cloud --list-locations oneandone
  83. description
  84. Description of the server.
  85. password
  86. Password of the server. Password must contain more than 8 characters
  87. using uppercase letters, numbers and other special symbols.
  88. power_on
  89. Power on server after creation. Default is set to true.
  90. firewall_policy_id
  91. Firewall policy ID. If it is not provided, the server will assign
  92. the best firewall policy, creating a new one if necessary. If the parameter
  93. is sent with a 0 value, the server will be created with all ports blocked.
  94. ip_id
  95. IP address ID.
  96. load_balancer_id
  97. Load balancer ID.
  98. monitoring_policy_id
  99. Monitoring policy ID.
  100. deploy
  101. Set to False if Salt should not be installed on the node.
  102. wait_for_timeout
  103. The timeout to wait in seconds for provisioning resources such as servers.
  104. The default wait_for_timeout is 15 minutes.
  105. public_key_ids
  106. List of public key IDs (ssh key).
  107. Functions
  108. =========
  109. * Create an SSH key
  110. .. code-block:: bash
  111. sudo salt-cloud -f create_ssh_key my-oneandone-config name='SaltTest' description='SaltTestDescription'
  112. * Create a block storage
  113. .. code-block:: bash
  114. sudo salt-cloud -f create_block_storage my-oneandone-config name='SaltTest2' description='SaltTestDescription' size=50 datacenter_id='5091F6D8CBFEF9C26ACE957C652D5D49'
  115. * Create a firewall policy
  116. .. code-block:: bash
  117. sudo salt-cloud -f create_firewall_policy oneandone name='1salt_test' description='salt_test_desc' rules='[{"protocol":"TCP", "port":"80", "description":"salt_fw_rule_descr"}]'
  118. For more information concerning cloud profiles, see :ref:`here
  119. <salt-cloud-profiles>`.