Closed benofben closed 7 years ago
This is getting closer. Open related issues are:
https://github.com/couchbase-partners/google-deployment-manager-couchbase/issues/21 https://github.com/couchbase-partners/google-deployment-manager-couchbase/issues/22
The display file is currently broken. Need to wire it into couchbase.py (replacing couchbase.jinja) once that is resolved.
Currently tracking a number of issues for this. Emily and Frank are looking into it.
I edited the display file some more. It’s in a state that’s close to the UI I’m aiming for, but it’s not rendering in the Partner Portal, which I assume means I broke it again. Can you help out with the syntax here?
https://github.com/couchbase-partners/google-deployment-manager-couchbase/tree/master/cloudlauncher
If we can get that working, next steps I see are:
Connect couchbase.py file to replace couchbase.jinja Resolve Service Account issue - https://github.com/couchbase-partners/google-deployment-manager-couchbase/issues/22 Resolve script import issue - https://github.com/couchbase-partners/google-deployment-manager-couchbase/issues/21
The service account issue is resolved. We still have the script issue - #21 and the display file is currently broken.
The script issue was resolved by flattening.
Current issues are:
I hit a stumbling block with setting the disk size. I don’t know why that isn’t working. I’d really like to show you the behavior I’m seeing and see if you have any ideas. To work around that I left the disk size as an un-validated integer and moved on. Here’s where I dropped the disk type and it started working again: https://github.com/couchbase-partners/google-deployment-manager-couchbase/commit/4d4cd9cb1cbbcee336da63ae975ee853ac56d86d
I’m not sure what to do about the plaintext couchbasePassword field. One solution would be to autogenerate the password, but if so we’d want to follow that approach in the DM template outside of Cloud Launcher as well so we didn’t split the codebase. Another approach would be a masked text field, but I think you mentioned that widget doesn’t exist.
The default deployment name is rather lengthy. That causes us to hit the 57 character limit for resource.baseInstanceName. I’m not really sure how to resolve that.
There’s a potential issue hiding in the defaultZone. If that zone has different machine types than the regions deployed in, the deployment will fail. I’m not sure if there’s a solution here.
Frank to look into pw masking. If not get password.py and integrate to output.
Not going to use the disk object, just using an int.
Frank to check on deployment length issue.
Ben to go over marketing copy and upload latest package.
I think our only gap is keys for hourly-pricing images. Once the keys are in place I can create the images. Both hourly-pricing and byol DM archives have been submitted.
In progress. Email thread with the last few issues is ongoing.
Done.
in progress....