PageRenderTime 26ms CodeModel.GetById 17ms RepoModel.GetById 0ms app.codeStats 0ms

/docs/providers.txt

https://bitbucket.org/ianb/silverlining/
Plain Text | 61 lines | 50 code | 11 blank | 0 comment | 0 complexity | 4bd5c5b44f33f829b02ea3c6171fbeda MD5 | raw file
Possible License(s): GPL-2.0 
    

  1. Cloud Provider Support
    2. 

  2. ======================
    3. 

  3. 

  4. This lists the cloud providers and the support available:
    5. 

  5. 

  6. Rackspace Cloud
    7. 

  7. ---------------
    8. 

  8. 

  9. `Rackspace <http://www.rackspace.com/cloud/?id=918>`_ is the
    10. 

  10. first (and currently only) provider supported by Silver Lining.
    11. 

  11. 

  12. To use Silver Lining you must sign up for an account through their
    13. 

  13. website.  You should sign up for "Cloud Servers" and "Cloud Files".
    14. 

  14. There's no initial fee, and the cost for experimenting with Silver
    15. 

  15. Lining will be less than a dollar as long as you don't forget to take
    16. 

  16. down the servers you create to experiment.  You'll have to have a
    17. 

  17. credit card, and Rackspace Cloud will call you to confirm your account
    18. 

  18. before you can use it.
    19. 

  19. 

  20. Once you have logged in go to **Your Account > API Access** to view or
    21. 

  21. create your API key.  Silver Lining needs to know your username and
    22. 

  22. API key, which it will ask you for when you first start the command.
    23. 

  23. 

  24. Host It Yourself
    25. 

  25. ----------------
    26. 

  26. 

  27. You don't *need* to use commands like ``silver create-node`` to make
    28. 

  28. use of Silver Lining.  If you have a machine with a fresh install of
    29. 

  29. Ubuntu Lucid then you can use ``silver setup-node`` to
    30. 

  30. configure the machine and ``silver update`` to deploy applications.
    31. 

  31. It's harder to test things without the ability to create and destroy
    32. 

  32. servers on demand, but the basic infrastructure is not really
    33. 

  33. dependent on that.
    34. 

  34. 

  35. **Don't use this on a server you want to keep!**  ``silver
    36. 

  36. setup-node`` is not aggressive in modifying the server, but it doesn't
    37. 

  37. particularly keep track of what it does, nor is there any reason it
    38. 

  38. should.  Also if you have local modifications on the server, those
    39. 

  39. modifications can be lost; all updates are done with the assumption
    40. 

  40. that it's being given a bare Ubuntu installation to work with.
    41. 

    42. 

  42. Other Providers
    43. 

  43. ---------------
    44. 

  44. 

  45. Silver Lining is built on `libcloud <http://libcloud.org>`_.  libcloud
    46. 

  46. abstracts over the API of quite a few cloud providers.  Any of these
    47. 

  47. providers should be a possible platform for Silver Lining; the basic
    48. 

  48. abstractions already exist, it just needs some testing.  The only
    49. 

  49. thing that's currently really Rackspace-specific is that on node
    50. 

  50. creation some files are uploaded -- not a complete set, mostly just
    51. 

  51. ``/root/.ssh/authorized_keys2``.  This is built in to some other APIs
    52. 

  52. (e.g., I believe EC2 node creation automatically sets up
    53. 

  53. authorized_keys).  It would require a bit of abstraction as a result.
    54. 

  54. 

  55. The best way to try a new provider is to fork the Silver Lining
    56. 

  56. repository, try it out, and make what patches are necessary --
    57. 

  57. probably to the routine that creates ``~/.silverlining.conf``
    58. 

  58. (:mod:`silverlining.createconf`), ``silver create-node``
    59. 

  59. (:mod:`silverlining.commands.create_node`), and *maybe* ``silver
    60. 

  60. setup-node`` (:mod:`silverlining.commands.setup_node`) -- though I
    61. 

  61. expect setup-node will be fine.
    62. 

  62.