Created a docs directory #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Docs directory for design docs, discussions, etc. Also added a basic README.
rkarthik007
pushed a commit
that referenced
this pull request
Aug 10, 2020
Summary: Implemented very basic Azure flow that doesn't allow for any customization.
Test Plan:
**Manual Postgres Hacks for Azure Flow to Work**
//Makes yugaware aware of Azure West US 2 region//
INSERT INTO yugaware_property (name, type, value, description) VALUES('AZURegionMetadata', 'Config', '{"westus2":{"name":"US West 2 (Folsom)","latitude":36.778261,"longitude":-119.417932}}', 'Azure Region Metadata');
//Enables Azure UI for *uuid* customer//
UPDATE users SET features = '{"universes": {"providers": {"azure": "enabled"}}}' WHERE uuid = *INSERT_UUID_HERE*;
**Other Hack in ~/.bashrc**
//Needed because provider bootstrap does not actually do any networking setup and we just always use this preset vnet/subnet in West (US) 2//
export AZURE_SUBNET="/subscriptions/*SUBSCRIPTION_ID*/resourceGroups/yugabyte-rg/providers/Microsoft.Network/virtualNetworks/yugabyte-vnet-us-west2/subnets/default"
SCENARIO #1:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 1 universe in a single AZ.
3. Verified YCQLSH with commands from https://docs.yugabyte.com/latest/api/ycql/dml_select/#syntax
4. Verified master/tserver UI along with proper number of active tablet peers.
5. Added a node to the universe.
6. Verify load was still balanced.
7. Delete Universe and ensure all related resource are deleted from Azure portal.
SCENARIO #2:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 3 universe with a single node in 3 different AZs
3. Verified YCQLSH with commands from https://docs.yugabyte.com/latest/api/ycql/dml_select/#syntax
4. Verified master/tserver UI along with proper number of active tablet peers.
5. Ensure the tables can be seen from all nodes.
6. Delete universe and verify in Azure portal.
SCENARIO #3:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 3 universe with a single node in 3 different AZs
3. 2. Create an RF 1 universe in a single AZ.
4. Ensure multiple universes do not interfere with each other.
5. Delete one universe at a time and the other is still functional.
Reviewers: bogdan, arnav, ram, wesley, sanketh
Reviewed By: wesley, sanketh
Subscribers: jenkins-bot, yugaware, muthu
Differential Revision: https://phabricator.dev.yugabyte.com/D8748
rkarthik007
pushed a commit
that referenced
this pull request
Aug 10, 2020
Summary: Adding in Azure support from the Java layer
Test Plan:
**Manual Postgres Hacks for Azure Flow to Work**
//Makes yugaware aware of Azure West US 2 region//
INSERT INTO yugaware_property (name, type, value, description) VALUES('AZURegionMetadata', 'Config', '{"westus2":{"name":"US West 2 (Folsom)","latitude":36.778261,"longitude":-119.417932}}', 'Azure Region Metadata');
//Enables Azure UI for *uuid* customer//
UPDATE users SET features = '{"universes": {"providers": {"azure": "enabled"}}}' WHERE uuid = *INSERT_UUID_HERE*;
**Other Hack in ~/.bashrc**
//Needed because provider bootstrap does not actually do any networking setup and we just always use this preset vnet/subnet in West (US) 2//
export AZURE_SUBNET="/subscriptions/*SUBSCRIPTION_ID*/resourceGroups/yugabyte-rg/providers/Microsoft.Network/virtualNetworks/yugabyte-vnet-us-west2/subnets/default"
SCENARIO #1:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 1 universe in a single AZ.
3. Verified YCQLSH with commands from https://docs.yugabyte.com/latest/api/ycql/dml_select/#syntax
4. Verified master/tserver UI along with proper number of active tablet peers.
5. Added a node to the universe.
6. Verify load was still balanced.
7. Delete Universe and ensure all related resource are deleted from Azure portal.
SCENARIO #2:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 3 universe with a single node in 3 different AZs
3. Verified YCQLSH with commands from https://docs.yugabyte.com/latest/api/ycql/dml_select/#syntax
4. Verified master/tserver UI along with proper number of active tablet peers.
5. Ensure the tables can be seen from all nodes.
6. Delete universe and verify in Azure portal.
SCENARIO #3:
1. Create an Azure Provider from UI using existing resource group yugabyte-rg (NOTE: Need to also create an AWS or GCP provider so that the key file can be selected from Create Universe UI)
2. Create an RF 3 universe with a single node in 3 different AZs
3. 2. Create an RF 1 universe in a single AZ.
4. Ensure multiple universes do not interfere with each other.
5. Delete one universe at a time and the other is still functional.
Reviewers: wesley, bogdan, arnav, ram, sshevchenko, sanketh
Reviewed By: sanketh
Subscribers: jenkins-bot, muthu, yugaware
Differential Revision: https://phabricator.dev.yugabyte.com/D8828
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docs directory for design docs, discussions, etc. Also added a basic README.