-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amp cluster management #519
Conversation
51e62b8
to
e1911d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docker: 1.13.0-rc2
freshly restored to factory defaults
docker swarm init
make install
./shrink.sh local
amp-cluster pf start --local -v
Result:
Service cluster-agent starting
Service cluster-server starting
Cluster services started
Connection to cluster server error: grpc: timed out when dialing
Reason:
my ~/.amp.yaml contains a normal serverAddress entry
The server address configuration needs to be independently set
//Execute commad | ||
cmd, _, err := RootCmd.Find(os.Args[1:]) | ||
if err != nil { | ||
g.printfc(colError, "Arg error: %v\n", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pattern of g.printfc(colError, errorDescription, err); os.exit(1)
is common enough make a g.fatalc(errorDescription, err)
method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, why not. I prefer explicit Exit command, than hidden one, but to be aligned with Go style, it's ok.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
follow = true | ||
} | ||
if follow { | ||
fmt.Println("\033[2J\033[0;0H") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These printlns are both arcane and used a number of places maybe a g.followStart(follow bool)
and g.followLn(follow bool)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
import "google/api/annotations.proto"; | ||
|
||
service ClusterServerService { | ||
rpc GetClientStream (stream ClientMes) returns (stream ClientMes) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
grpc-gw annotations would be nice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes sure, but first get agreement on the cli verbs/structure and inclusion or not in amp cli.
About server address configuration, i was waiting the decisions to merge or not the cluster-cli into amp-cli or cluster-server into amplifier to finalize the configuration (see the discussion topic "Short demo on amp cluster features" on Mobilize), but in the meantime i can make it separated yes. |
7194405
to
f1c929f
Compare
1d0f21d
to
587dd56
Compare
587dd56
to
715185a
Compare
a878678
to
9949323
Compare
9949323
to
4954fc8
Compare
b91b920
to
bebdb41
Compare
* add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff)
9e3fcad
to
0b6c1bd
Compare
@freignat91 @ndegory It's taken a while for me to review, but excellent work. Thank you for this contribution. 👍 I'm merging this into v0.5.0-rc1 for now for additional evaluation. |
* add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff)
* commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * serverless prototype (#539) * Amp cleanup (#603) * Fix for issues #547,#561,#565 * minor cleanup * commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * serverless prototype (#539) * Amp version more useful info
* add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff)
* add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff)
* commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * serverless prototype (#539) * commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * Revert "Amp version command - more useful info" (#611) * Add functions to the ui (#605) * KV ui (#606) * Add functions to the ui * add kv to ui * bump version to 0.6.0-dev * Added amp help command (#652) * Included Long message in help command output * remerge version
* commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * serverless prototype (#539) * commit server,agents,clients, AMP Bootstrap and fixes reports (#519) * add bootstrap feature to AMP cluster CLI (#306) * update vendors (huge diff) * Revert "Amp version command - more useful info" (#611) * Add functions to the ui (#605) * KV ui (#606) * Add functions to the ui * add kv to ui * bump version to 0.6.0-dev * Added amp help command (#652) * Included Long message in help command output * remerge version
Related to #512
For the ones granted, here is a video to explain more in details the PR features
https://drive.google.com/a/axway.com/file/d/0B3HdJx5HHXGcUzR1ZVRSMGVURVk/view?usp=sharing
see also the discussion on the topic "Short demo on amp cluster features" on Mobilize
to test locally:
make install
./shrink.sh local
ampadm pf pull --local -v
ampadm pf start --local -v
ampadm pf monitor
(on another console)ampadm node ls
ampadm node count
ampadm pf stop
to test on Amazon amp cluster after having used the Nicolas's amp-bootstrap installation:
On the manager execute:
ampadm cluster start --tag cluster
(it use a predefined amp:cluster image for PR need, but after merge and image appelerator/amp:latest built and pulled no need of the option "--tag cluster")
That's all on manager.
on your laptop client machine execute:
ampadm --server [managerAddress]:31315 node ls
(to see the nodes status)ampadm --server [managerAddress]:31315 node purge --container --image
(if needed)ampadm --server [managerAddress]:31315 pf pull -v
(all amp images are pulled on all nodes)ampadm --server [managerAddress]:31315 pf start -v
ampadm --server [managerAddress]:31315 pf monitor
(on another console)[managerAdresse] can be an aws load-balancer address
For now the previous amp pf commands stay available, waiting for decision about amp/amp-cluster cli integration or not.
-ampadm --server [managerAddress]:31315 pf pull -v