Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Change-Id: Ie76c6fe26622ca8363055b8ebbe0dc6deaed5824
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
This commit hides bookings that have ended from cluttering
the "My Bookings" page.
Change-Id: I0f98fbff97b1474e73a666aa0000e1923266fafb
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
Change-Id: I8ca860ee23f9df44e38da76d539729771d32c455
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
|
|
Change-Id: I1186429df8989461e2384f1f3e533c55cebfb1b4
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
A user can now delete thier own resources, configs,
and snapshots as well as cancelling bookings.
Change-Id: Ic8e4751feeb0b8fa0d76816b8df2d16729ad2828
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
This change adds a button the user can press on thier booking
detail page to reset thier host. They can choose to deploy
any available image to thier servers (not just the one already used)
Change-Id: I97a9869d2b38389c54f13173bb28a68cc52bb8d5
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
Users can now quickly provision a single-host pod without having to
configure unecessary networking. This is intended to be analogous to the
workflow used during LaaS 1.0, and to speed up the process of creating a
booking for users who do not need more than a single host (for virtual
deployments)
Change-Id: Ia19cea9a42bbb1df57aad05af8f8ea821395664d
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
The flake8 command in test.sh finds no longer finds any errors.
This may form a basis of a jenkins verify job as a sort of 'weak compile-time checks'
The flake8 command will not complain about line length, and will not complain about
django's manage.py file
Change-Id: Ic47cb4fc7ada55e64485661ab6881aef475018ff
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
See changes here:
https://wiki.opnfv.org/display/INF/Pharos+Laas
Change-Id: I59ada5f98e70a28d7f8c14eab3239597e236ca26
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
Since these are in the .gitignore file they shouldn't be in the repo.
Change-Id: Iaf4da94863d4edf10bdce924d33023ca2d679c64
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Jira: PHAROS-347
Resources are now possible to associate with lab instances upon creation
Change-Id: Id8abbcc448a6d840d55e4bf5130dbec22c8bc58f
|
|
Jira: PHAROS-330
Users can change start date if it has not already occurred, and
can change end date, purpose, and both installer and scenario.
Standard checks apply similar to when initially creating a booking.
Change-Id: Ibae7fe91a58bd6e0741db065265c05c3823bdc27
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
|
|
Jira: PHAROS-346
Allows admin to instantiate lab instances
Change-Id: I67f8ceb3bc76d4cdd09fb6f3a0b715af312f6f83
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
|
|
JIRA: None
Notification/notifier objects are now created with title,
content, sender, associated resource, and recipient and there is
now support for emails at the very least to be sent as notifications.
Change-Id: I456cf0e901d9a1e2a1e7d187dcc03d28fca003fb
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
|
|
JIRA: None
Integrate ability for users to change email presented to admins
with field initially filled with user's Jira associated email address
This amend takes into account a streamlining change
suggested by Parker Berbarian
Change-Id: I677ce669f200e5cad70c198737118f0b7925bac5
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
|
|
As subdirectories of the pharos-tools repo, there is little need to keep
the pharos prefix.
Change-Id: Ica3d79411f409df638647300036c0664183c2725
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|