forked from redhat-performance/quads
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Demo 5 branch #49
Closed
Closed
Demo 5 branch #49
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
Isaac branch
awesome
deleting test.txt
adding test-quads-local.sh from course repo
Extend for hil api
committing testing.txt for git workflow demo
added testing.txt for git workflow
The current notifications are not sent for the initial release unless specific tests are passed with the environment. The initial pass at addressing this checks the QinQ and untagged traffic for the given environment. The changes to the notification is coupled with a cron based check to ensure the env has passed the initial network test. Once it can be "released", the releasability is marked using a combination of env-owner-ticket marker (unique for every allocation). Fixes: redhat-performance#5 Change-Id: I67fa8d2bf176df50b1f8947825525cdeffa24430
load write sync init (c)Vlad
Instantiate concrete subclasses
added .DS_Store to gitignore
Created a pytest for mock interface driver and running into issues with init, so pushing to get remote to get more eyes on it.
The old code took over an hour to regenerate the visualization maps. This will make it run in 3 seconds per month. Fixes: redhat-performance#56 Change-Id: I87bfa7228cc396363b36625902e6707898927fda
This commit is enablement for two things: 1) View "heat-map" like view of schedule per-month 2) Allow for dynamic generation of the heat-map Fixes: redhat-performance#57 Change-Id: I25317dcbec0b04bbd89ed30bcfebddb88640814c
This change is to have bin/simple-table-web.sh, a wrapper script to generate the visualization maps, call bin/simple-table-generator.py directly instead of another shell script. This change deprecates the need to continue to include bin/simple-table-generator.sh (which will likely be removed in a future change). Change-Id: I050362de4c34ef025d2dd39031b59b375a36befc
quads without any args produces the schedule in yaml output. the --schedule-query introduced changed the default behavior. This is a small patch to change the default behavior and treats the new arg as a toggle for producing the schedule. --month and --year are optional and default to the current time's month and year. Change-Id: I7ebd47eb1a84a4894a3a482ca6654e834f713914
This is the PyTest that can be used to test the MockInventory Driver for Demo4. Pushing up for better testing from others.
PyTest for MockInventoryDriver for Demo4
Mock inventory update
This change preserves the cloud definitions in the data stored on disk similar to the host history information. For example, as allocations are used, and expire, and later for a new project the cloud environment is redefined, cloud_history allows for looking backwards and seeing what the previous allocation was used for. Specifically in the schedule.yaml, there will be a new section that looks something like this: cloud_history: cloud01: 0: ccusers: [] description: Pool of available servers owner: nobody qinq: '0' ticket: '000000' [...] cloud07: 0: ccusers: [] description: AMQ OpenStack owner: mwagner qinq: '0' ticket: '429833' 1492047523: ccusers: [] description: AMQ OpenStack owner: mwagner qinq: '0' ticket: '429833' Then when you query for the summary (or full summary), when using the --date string with a date/time in the past you will correctly see the previously defined name of the environment. e.g. $ ./bin/quads.py --full-summary --date "2017-04-12 21:00" cloud01 : 36 (Pool of available servers) cloud02 : 10 (OSP Metrics/Memory Calc) cloud03 : 15 (Gluster RHGS FIO) cloud04 : 0 (OSP and NW roles) cloud05 : 37 (Satellite) cloud06 : 0 (OSP RHCS) cloud07 : 28 (AMQ OpenStack) cloud08 : 0 (OSP10 Testing) cloud09 : 0 (RHCS2.0/HCI) cloud10 : 0 (Openshift + OSPD testing) cloud11 : 0 (OSP BZs) cloud12 : 12 (OSP10 + HCI + RHCS) cloud13 : 0 (JBoss EAP) cloud14 : 13 (ODL OSP) cloud15 : 0 (OSP storage) cloud16 : 36 (OSP11 Ocata) $ ./bin/quads.py --full-summary cloud01 : 36 (Pool of available servers) cloud02 : 10 (OSP Metrics/Memory Calc) cloud03 : 15 (Gluster RHGS FIO) cloud04 : 0 (OSP and NW roles) cloud05 : 37 (Satellite) cloud06 : 0 (OSP RHCS) cloud07 : 28 (Another Random allocation) cloud08 : 0 (OSP10 Testing) cloud09 : 0 (RHCS2.0/HCI) cloud10 : 0 (Openshift + OSPD testing) cloud11 : 0 (OSP BZs) cloud12 : 12 (OSP10 + HCI + RHCS) cloud13 : 0 (Random allocation) cloud14 : 13 (ODL OSP) cloud15 : 0 (OSP storage) cloud16 : 36 (OSP11 Ocata) Notice that cloud07 and cloud13 were redefined in the test data yet looking backward, we can see the previously assigned name. Fixes: redhat-performance#58 Change-Id: Ib7d034de5cb2cd79e336a977e321970a6cb477ff
Hovering over the cells in the visualization map will now give the following information: Description env name owner RT Fixes: redhat-performance#9 Fixes: redhat-performance#59 Change-Id: Icf89f5e39669f9e5bcc71e7d16d24394d9e6fecf
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.
No description provided.