Commit Graph

15 Commits

Author SHA1 Message Date
Andreas Jaeger 24120d7b66 Retire repository
Fuel (from openstack namespace) and fuel-ccp (in x namespace)
repositories are unused and ready to retire.

This change removes all content from the repository and adds the usual
README file to point out that the repository is retired following the
process from
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

See also
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011647.html

Depends-On: https://review.opendev.org/699362
Change-Id: Ibd0360edc1781ea748a1ef28877c215bb4c726c7
2019-12-18 09:38:32 +01:00
Andrey Pavlov c8cffc034f Fixing ccp status
Change-Id: Ib37d880a2c506950b11518e2e5ffd0834c2e19f1
2017-03-21 15:17:36 +04:00
Andrey Pavlov b5b0196ee6 Adding statefulsets to ccp status
Change-Id: I993f174109f3d02aa2c5243dce2b82615983876d
2017-03-16 17:05:39 +04:00
Andrey Pavlov 24ebafb214 Check if nodePort exists
Change-Id: Iec64aea75ac6d0afdf2943855227e2b8c2230d2a
2017-03-07 18:38:46 +04:00
Andrey Pavlov 436655c030 Remove -l param from ccp status command
There's no additional information provided with -l param,
so it can be removed. Also "no cluster" message changed to
"not deployed".

Change-Id: Id0f3cf4b873eb3d5d9e59ed5f7d6fd6fec947887
2017-01-29 13:06:41 +00:00
Andrey Pavlov a82271fc90 Fixing ccp status -s when components provided
ccp status -s will show short status of provided components only
(instead of the whole cluster status)

Change-Id: Ib464c4a2eaaf2ab08c19b5e5add4cb79879794cf
2017-01-29 12:57:08 +00:00
Sergey Reshetnyak 25dd3eeb38 Do not show action status in 'ccp status' output
Use 'ccp action status' for showing action statuses

Change-Id: I938a0c3c6d0a733bf557a70b26ad6bec97168583
2017-01-17 16:45:28 +03:00
Sergey Reshetnyak 53c58ac61b Fix getting replicas count in ccp status
replicas key is not available in status info during creating and
upgrading deployment

Change-Id: I6dd02630a8e7d7fa39e9676ba0e53456e25b9ce5
2016-11-24 17:00:16 +03:00
Sergey Reshetnyak e78d1e3b06 Check service status via deployments
After migration on Deployments we can use deployment objects for
checking service status.

Change-Id: I78b85a1de787a38d100c6f8dd4972c626fc4c188
2016-11-15 16:34:53 +03:00
Sergey Reshetnyak 0800f10ec0 Show correct url in status if ingress enabled
Change-Id: I0207d8be1394634e5da4c23bb2d15e05044d53fd
2016-11-11 18:10:13 +03:00
Sergey Reshetnyak f0911697bb Make ready column colorized in status output
Also nok changed to wip
Demo: http://asciinema.org/a/1cchitobrzp7k0fh2jdtrrvhb

Change-Id: Icd3a9884c91e804ad58aec81a2b0013c04a14db5
2016-11-11 18:09:12 +03:00
Sergey Reshetnyak e51f254eda Optimize 'ccp status' command
Now it works for 3 requests instead deployment_count + daemonset_count +
3 requests

Change-Id: Icb941c183ed05d3686667b7fa1644bebea684077
2016-11-11 18:07:47 +03:00
Andrey Pavlov 95d2484ed4 Drop DaemonSet support
DaemonSet objects will be replaced with Deployment objects,
but one-pod-per-node rule will be provided with pod
antiaffinity and replicas will be set to number of matched
nodes.

Change-Id: Ieb8ac38e8d4426dd66668dbee303592137ce7fa0
2016-11-10 15:48:16 +03:00
Sergey Reshetnyak 88df51b55d Add job statuses in 'ccp status' command
Added new column 'job' that shows status of jobs

Change-Id: Ic8b320d60290816bc02e743a0cb93031c67c15d2
2016-11-09 19:28:21 +03:00
Sergey Reshetnyak c76ec7a9fe Add status command
status command allows to show deployments and daemonset statuses

Change-Id: Iaf2f7d23b9ad1e54f512c63c224cb79cb78a76f3
2016-10-25 12:34:50 +03:00