I can only imagine

I can only imagine what it will be like, when I walk by Your side...
I can only imagine, what my eyes will see, when Your Face is before me!
I can only imagine. I can only imagine.

Surrounded by Your Glory, what will my heart feel?
Will I dance for you, Jesus? Or in awe of You, be still?
Will I stand in Your presence, or to my knees will I fall?
Will I sing 'Hallelujah!'? Will I be able to speak at all?
I can only imagine! I can only imagine!

I can only imagine, when that day comes, when I find myself standing in the Son!
I can only imagine, when all I will do, is forever, forever worship You!
I can only imagine! I can only imagine!

Surrounded by Your Glory, what will my heart feel?

Will I dance for you, Jesus? Or in awe of You, be still?
Will I stand in Your presence, or to my knees will I fall?
Will I sing 'Hallelujah!'? Will I be able to speak at all?
I can only imagine! Yeah! I can only imagine!

Surrounded by Your Glory, what will my heart feel?

Will I dance for you, Jesus? Or in awe of You, be still?
Will I stand in Your presence, or to my knees will I fall?
Will I sing 'Hallelujah!'? Will I be able to speak at all?
I can only imagine! Yeah! I can only imagine!

I can only imagine! Yeah! I can only imagine!! Only imagine!!!
I can only imagine.

I can only imagine, when all I do is forever, forever worship You!
I can only imagine.

Another example is the SRIOV_NET_VF resource class, which is provided by SRIOV-enabled network interface cards. In the case of multiple SRIOV-enabled NICs on a compute host, different qualitative traits may be tagged to each NIC. For example, the NIC called enp2s0 might have a trait “CUSTOM_PHYSNET_PUBLIC” indicating that the NIC is attached to a physical network called “public”. The NIC enp2s1 might have a trait “CUSTOM_PHYSNET_INTRANET” that indicates the NIC is attached to the physical network called “Intranet”. We need a way of representing that these NICs each provide SRIOV_NET_VF resources but those virtual functions are associated with different physical networks. In the resource providers data modeling, the entity which is associated with qualitative traits is the resource provider object. Therefore, we require a way of representing that the SRIOV-enabled NICs are themselves resource providers with inventories of SRIOV_NET_VF resources. Those resource providers are contained on a compute host which is a resource provider that has inventory records for other types of resources such as VCPU, MEMORY_MB or DISK_GB. This spec proposes that nested resource providers be created to allow for distinguishing details of complex components of some resource providers. During review the question came up about “rolling up” amounts of these nested providers to the root level. Imagine this scenario: I have a NIC with two PFs, each of which has only 1 VF available, and I get a request for 2 VFs without any traits to distinguish them. Since there is no single resource provider that can satisfy this request, it will not select this root provider, even though the root provider “owns” 2 VFs. This spec does not propose any sort of “rolling up” of inventory, but this may be something to consider in the future. If it is an idea that has support, another BP/spec can be created then to add this behavior.
07-23
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值