Note this should only be done once you are sure you have reliable TB mesh network.
this is because proxmox UI seems fragile wrt to changing underlying network after configuration of ceph.
All installation done via command line due to gui not understanding the mesh network
This setup doesn't attempt to seperate the ceph public network and ceph cluster network (not same as proxmox clutser network), The goal is to get an easy working setup.
I hereby claim:
To claim this, I am signing this object:
| #!/usr/bin/env python3 | |
| import socket | |
| import requests | |
| from subprocess import Popen, PIPE | |
| import json | |
| # These lines are examples only. They may be useful to compare what your remote sends. To capture the codes that your remote sends, | |
| # tail the OZW_Log. |
| Outputs: | |
| s3bucketurl: | |
| Description: URL for Bucket | |
| Value: !GetAtt s3bucket.WebsiteURL |
| Resources: | |
| s3bucket: | |
| Type: "AWS::S3::Bucket" | |
| Properties: | |
| AccessControl: PublicRead | |
| WebsiteConfiguration: | |
| ErrorDocument: index.html | |
| IndexDocument: index.html | |
| bucketpolicy: | |
| Type: "AWS::S3::BucketPolicy" |
