[logseq-plugin-git:commit] 2025-12-11T14:50:38.767Z

This commit is contained in:
2025-12-11 06:50:39 -08:00
parent c410d39336
commit 4c8bba878d
551 changed files with 0 additions and 14608 deletions

View File

@@ -1,27 +0,0 @@
- I178
- TODO Review [Marketables](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=%2Fportfolioitem%2Finitiative%2F707097204937%2Fchildren) #Equinix
SCHEDULED: <2024-02-07 Wed ++1w>
:LOGBOOK:
* State "DONE" from "TODO" [2024-02-04 Sun 21:42]
* State "DONE" from "TODO" [2024-02-06 Tue 15:31]
* State "DONE" from "TODO" [2024-02-06 Tue 15:32]
* State "DONE" from "TODO" [2024-02-06 Tue 15:33]
:END:
- ## [M1806 - PCE@Colo - PCE expansion](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/730392607969)
- reviewed use case / requirements [[Jan 30th, 2024]]
- Followup with Dave/Juston on multi-rack netwokr issue
- Stuart Stent  [14:58](https://hpe-internal.slack.com/archives/C053K1UU0M7/p1706644723588099) did we ever solve the multi-rack network issue for PCE @ Equinix? or are we still stuck at single rack? `note: this has implications on prioritization of marketable for expansion of PCE in the rack`
- Justin said that GLMetal still and issues (might be possible to do 2 racks, but lots of unknowns - e.g. when you add a new virt network what happens)
- ## [M1796 - @Colo - Network rack deployment](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
- ## [M1627 - PCE@Colo - Colo Billing tracking and reporting service](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
-
- ## [M1620 - PCE@Colo - PCE instance reconfigure](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/705545594519)
-
- ## [M1617 - Colo - Network Rack Operations](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704650808469)
-
- ## [M1615 - Colo - Inventory reporting system](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704561630707)
- TODO Meet with Equinix re Monetization events
SCHEDULED: <2024-03-01 Fri>
-

View File

@@ -1,27 +0,0 @@
- I178
- TODO Review [Marketables](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=%2Fportfolioitem%2Finitiative%2F707097204937%2Fchildren) #Equinix
SCHEDULED: <2024-02-07 Wed ++1w>
:LOGBOOK:
* State "DONE" from "TODO" [2024-02-04 Sun 21:42]
* State "DONE" from "TODO" [2024-02-06 Tue 15:31]
* State "DONE" from "TODO" [2024-02-06 Tue 15:32]
* State "DONE" from "TODO" [2024-02-06 Tue 15:33]
:END:
- ## [M1806 - PCE@Colo - PCE expansion](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/730392607969)
- reviewed use case / requirements [[Jan 30th, 2024]]
- Followup with Dave/Juston on multi-rack netwokr issue
- Stuart Stent  [14:58](https://hpe-internal.slack.com/archives/C053K1UU0M7/p1706644723588099) did we ever solve the multi-rack network issue for PCE @ Equinix? or are we still stuck at single rack? `note: this has implications on prioritization of marketable for expansion of PCE in the rack`
- Justin said that GLMetal still and issues (might be possible to do 2 racks, but lots of unknowns - e.g. when you add a new virt network what happens)
- ## [M1796 - @Colo - Network rack deployment](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
- ## [M1627 - PCE@Colo - Colo Billing tracking and reporting service](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
-
- ## [M1620 - PCE@Colo - PCE instance reconfigure](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/705545594519)
-
- ## [M1617 - Colo - Network Rack Operations](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704650808469)
-
- ## [M1615 - Colo - Inventory reporting system](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704561630707)
- TODO Meet with Equinix re Monetization events
SCHEDULED: <2024-03-01 Fri>
-

View File

@@ -1,27 +0,0 @@
- I178
- TODO Review [Marketables](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=%2Fportfolioitem%2Finitiative%2F707097204937%2Fchildren) #Equinix
SCHEDULED: <2024-02-07 Wed ++1w>
:LOGBOOK:
* State "DONE" from "TODO" [2024-02-04 Sun 21:42]
* State "DONE" from "TODO" [2024-02-06 Tue 15:31]
* State "DONE" from "TODO" [2024-02-06 Tue 15:32]
* State "DONE" from "TODO" [2024-02-06 Tue 15:33]
:END:
- ## [M1806 - PCE@Colo - PCE expansion](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/730392607969)
- reviewed use case / requirements [[Jan 30th, 2024]]
- Followup with Dave/Juston on multi-rack netwokr issue
- Stuart Stent  [14:58](https://hpe-internal.slack.com/archives/C053K1UU0M7/p1706644723588099) did we ever solve the multi-rack network issue for PCE @ Equinix? or are we still stuck at single rack? `note: this has implications on prioritization of marketable for expansion of PCE in the rack`
- Justin said that GLMetal still and issues (might be possible to do 2 racks, but lots of unknowns - e.g. when you add a new virt network what happens)
- ## [M1796 - @Colo - Network rack deployment](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
- ## [M1627 - PCE@Colo - Colo Billing tracking and reporting service](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/729584910367)
-
-
- ## [M1620 - PCE@Colo - PCE instance reconfigure](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/705545594519)
-
- ## [M1617 - Colo - Network Rack Operations](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704650808469)
-
- ## [M1615 - Colo - Inventory reporting system](https://rally1.rallydev.com/#/316925971404ud/dashboard?detail=/portfolioitem/marketable/704561630707)
- TODO Meet with Equinix re Monetization events
SCHEDULED: <2024-03-01 Fri>
-