Datasets:
willtheorangeguy
/
2017-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.49k
[1742.60 --> 1743.34] one component
[1743.34 --> 1744.06] that's required
[1744.06 --> 1745.26] is the
[1745.26 --> 1746.10] Bosch piece.
[1747.18 --> 1747.88] Bosch, if
[1747.88 --> 1748.16] you're not
[1748.16 --> 1748.76] familiar with
[1748.76 --> 1749.18] it, is a
[1749.18 --> 1749.44] lifecycle
[1749.44 --> 1750.46] manager for
[1750.46 --> 1751.28] applications,
[1752.12 --> 1752.62] and so
[1752.62 --> 1754.00] it's something
[1754.00 --> 1754.50] that will
[1754.50 --> 1755.12] monitor your
[1755.12 --> 1756.00] application or
[1756.00 --> 1756.98] your infrastructure,
[1758.02 --> 1758.52] if something
[1758.52 --> 1759.06] goes wrong,
[1759.14 --> 1759.60] it's going to
[1759.60 --> 1760.26] take immediate
[1760.26 --> 1760.90] action.
[1761.72 --> 1763.14] So if one
[1763.14 --> 1763.60] of the nodes
[1763.60 --> 1764.00] becomes
[1764.00 --> 1764.74] unresponsive,
[1764.78 --> 1765.26] for example,
[1765.88 --> 1767.60] or some
[1767.60 --> 1768.40] failure condition
[1768.40 --> 1769.14] happens, it's
[1769.14 --> 1769.70] going to try to
[1769.70 --> 1770.22] restart the
[1770.22 --> 1770.66] processes.
[1770.88 --> 1771.06] If the
[1771.06 --> 1772.98] processes aren't
[1772.98 --> 1773.38] to blame,
[1773.44 --> 1773.78] it's going to
[1773.78 --> 1774.50] recreate the
[1774.50 --> 1774.70] VM.
[1775.66 --> 1777.06] So that's in a
[1777.06 --> 1777.60] nutshell what it
[1777.60 --> 1777.78] does.
[1777.88 --> 1778.22] So it's a
[1778.22 --> 1778.98] managed unattended
[1778.98 --> 1779.58] version of
[1779.58 --> 1779.98] Kubernetes.
[1780.44 --> 1780.92] Earlier,
[1781.18 --> 1782.44] somebody mentioned
[1782.44 --> 1784.26] that operating
[1784.26 --> 1784.82] these things
[1784.82 --> 1785.98] is annoying.
[1786.56 --> 1786.88] This is
[1786.88 --> 1787.48] exactly the
[1787.48 --> 1787.92] type of
[1787.92 --> 1788.68] intelligence we
[1788.68 --> 1789.16] are trying to
[1789.16 --> 1789.88] encapsulate in
[1789.88 --> 1790.46] that project.
[1791.14 --> 1792.76] It takes away
[1792.76 --> 1793.46] the operational
[1793.46 --> 1794.80] heart headaches
[1794.80 --> 1795.10] of it.
[1795.60 --> 1796.48] It will also
[1796.48 --> 1797.50] do zero
[1797.50 --> 1798.74] downtime upgrades
[1798.74 --> 1799.44] and so on
[1799.44 --> 1800.66] over time.
[1801.92 --> 1802.82] I think that's
[1802.82 --> 1803.32] in a nutshell
[1803.32 --> 1804.08] what PKS
[1804.08 --> 1804.52] is.
[1805.88 --> 1807.42] Other than
[1807.42 --> 1807.90] that, we
[1807.90 --> 1808.76] make sure that
[1808.76 --> 1809.58] it can leverage
[1809.58 --> 1811.20] just all of
[1811.20 --> 1811.88] this stuff that
[1811.88 --> 1812.66] VMware already
[1812.66 --> 1814.56] has, like a
[1814.56 --> 1815.32] login site for
[1815.32 --> 1816.36] log aggregation
[1816.36 --> 1818.58] and Wavefront
[1818.58 --> 1819.24] for metrics
[1819.24 --> 1820.14] aggregation and
[1820.14 --> 1820.70] so forth.
[1822.32 --> 1823.92] I'm employed
[1823.92 --> 1824.40] by VMware
[1824.40 --> 1825.02] after all.
[1825.78 --> 1826.28] Well, that
[1826.28 --> 1826.78] makes sense.
[1827.42 --> 1828.50] So on the
[1828.50 --> 1830.38] networking side,
[1830.44 --> 1831.16] does it use
[1831.16 --> 1832.88] VMware's networks
[1832.88 --> 1834.22] or Kubernetes
[1834.22 --> 1835.08] overlays?
[1836.12 --> 1836.56] Oh, yes.
[1836.62 --> 1836.84] Sorry.
[1837.00 --> 1837.66] Yes, it does
[1837.66 --> 1838.92] NSX-T.