1. 28 May, 2020 6 commits
  2. 27 May, 2020 3 commits
  3. 26 May, 2020 7 commits
  4. 25 May, 2020 7 commits
  5. 22 May, 2020 1 commit
    • Jérome Perrin's avatar
      Proxy: Forward requests as partition and use it in standalone · e0b4339e
      Jérome Perrin authored
      The idea is to make it possible while embedding SlapOS in an existing partition to configure that some requests are forwarded to the master of the partition and to make these requests as the partition - so that when this partition is destroyed all other partitions from the embedded partitions are destroyed.
      
      A bit more integration in slapos is still needed, but is intended to be used in theia (and why not webrunner):
      
      At the beginning theia's instance  looks like this:
      
      ![screenshot of theia hosting subscription on slapos master, with the default 3 partitions](/uploads/9a297dbbae49996fb7ee69e89ea75da1/image.png)
      
      after an ERP5 instance is requested in theia's embedded slapos, the partition requests are forwarded as this partition and appear here, as requested by theia:
      
      ![screenshot of theia hosting subscription on slapos master, frontend partitions requested by ERP5 appears as requested by theia](/uploads/37b8b30ca117a1251fc2bd099a5dac82/image.png)
      
      This can also allow transparent integration, because the partition credentials are known by the partition, unlike the user credentials.
      
      See merge request !218
      e0b4339e
  6. 20 May, 2020 8 commits
  7. 19 May, 2020 1 commit
  8. 18 May, 2020 1 commit
  9. 15 May, 2020 4 commits
  10. 14 May, 2020 2 commits
    • Rafael Monnerat's avatar
      Master: Include authentification Policy BT5 · 7862ea47
      Rafael Monnerat authored
        slapos_erp5: Add erp5_authentication_policy as project dependency
        slapos_cloud: Define standard configuration for authentication policy
        Update tests on various bt5.
      7862ea47
    • Rafael Monnerat's avatar
      slapos_subscription_request: Refactor Subscription Request workflow · e95da4ac
      Rafael Monnerat authored
        Modifies the Workflows meaning for Support Request Workflow
      
          Draft: Reservation isn't Payed, Person is created
          Planned: Reservation is Payed, User is going to be Notified
          Ordered: First month isn't payed, Hosting Subscription is created
                   (started), user is notified about the payment to be done.
      
          Confirmed: Hosting Subscription is stopped until the payment
                     is done. Once it done, instance is started and
                     user is Notified.
      
          Started: User is available for this user.
      
          Stopped/Delivered aren't implemented.
      
        Nothing is implemented inside the workflow itself, alarms calls the
        scripts which changes the transitions once everything is ready to move
        foward.
      
        Allocation aoccur when if subscription request is in ordered state. We
        allocate earlier to reserve the space until the payment is done.
      e95da4ac